Overview
What is Amazon API Gateway?
AWS offers the Amazon API Gateway supports the creation and publication of an API for web applications, as well as its monitoring and maintenance. The Amazon API Gateway is able to support thousands of API calls concurrently and provides traffic…
The API that everyone needs.
Amazon API Gateway - Right tool for web services development
API Gateway is Great for Integrating REST and HTTP Access to Other AWS Resources
API Gateway - Easy to manage or not?
AWS API Gateway is a solid solution to orchestrate your web services.
It is not as easy to integrate as they tell you
Amazon API Gateway is great for your API needs
API Gateway provides Scalable, Secured, and Well Integrated Endpoints!
Amazon API Gateway : Secure, Scalable and Robust service
Scalable, robust and efficient entry point to the world of AWS services
It offers an intuitive easy-to-use entry point to the AWS …
API Gateway - Great web toolkit for publishing APIs
A Powerful Tool for Developing Micro-Services Rapidly
Popular Features
- API usage data (12)8.383%
- API monitoring and logging (13)7.676%
- Rate limits and usage policies (12)7.070%
- API access control (12)6.666%
Pricing
Past 300 Million
$0.90
First 300 Million
$1.00
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Features
API Management
API management handles technical things like user permissions, version control,and security, in addition to business items like documentation and pricing
- 6.6API access control(12) Ratings
Authentication and authorization systems to ensure that users of the API have permission
- 7Rate limits and usage policies(12) Ratings
Usage quotas to restrict traffic volumes to keep traffic loads manageable
- 8.3API usage data(12) Ratings
Analysis of traffic patterns to track how API is being used
- 8.3API user onboarding(12) Ratings
Systems to allow users to sign up, receive access credentials and be assigned usage rights
- 9.3API versioning(12) Ratings
There are mechanisms to roll out new versions of the API and the ability to migrate applications to new versions.
- 7.8Usage billing and payments(11) Ratings
Support for payment mechanisms such as monthly fees, or other payment patterns
- 7.6API monitoring and logging(13) Ratings
Regular test cycles to check that APIs are operating as expected and log analysis providing deeper analysis on system usage
Product Details
- About
- Tech Details
- FAQs
What is Amazon API Gateway?
Amazon API Gateway Technical Details
Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
---|---|
Operating Systems | Unspecified |
Mobile Application | No |
Frequently Asked Questions
Comparisons
Compare with
Reviews and Ratings
(100)Attribute Ratings
Reviews
(1-4 of 4)The API that everyone needs.
- Hosting REST APIs that follow HIPPA guidelines and regulations.
- It provides mock responses that help keep check of the automation scenario and reality.
- It is easy to use and can be customized as per requirements.
- The service and support are mediocre at best.
- It is very hard to debug when something in the code is incorrect..
- Various programming languages are missing.
- A centralized management system.
- It provides mock responses, which help relate automated scenarios to reality.
- Its capability to integrate with multiple web services and applications.
- API access control
- 80%8.0
- Rate limits and usage policies
- 70%7.0
- API usage data
- 90%9.0
- API user onboarding
- 90%9.0
- API versioning
- 100%10.0
- Usage billing and payments
- 100%10.0
- API monitoring and logging
- 90%9.0
- It helped a lot in increasing productivity.
- Work efficiency increased.
- Productivity sometimes takes a major hit due to a lack of programming languages.
The main problem that API GW addresses for us is providing an authorization management point for access to internal services. We can use the API keys, authorization hooks, and usage plans to really dial in who can access our applications while controlling how they access them.
- Swagger integration
- Rate limiting
- API key management
- Lambda Integration
- Testing and rapid development
- Client certificates are troublesome when trying to attach them to API GW stages.
- Debugging across several services can be difficult when API GW is integrated with Route 53 and another service like Lambda or EC2/ELB.
- Creating internal/private APIs, particularly with custom domains, can be unintuitive.
In the past, an operation that is called on via an HTTP endpoint would be implemented using a server-based solution. With high availability in place that would include a server or two and a load balancer. Over time this setup can be costly, especially if the service is not used at full capacity; cycles are wasted when the servers are sitting there waiting to respond.
If the operation can be distilled down to a function, an API GW + Lambda solution could be put in place that performs the operation as needed only when requested. Comparing the low price point for API GW requests and Lambda CPU+Memory, the savings can be night and day over the server-based implementation.
- API access control
- 100%10.0
- Rate limits and usage policies
- 100%10.0
- API usage data
- 80%8.0
- API user onboarding
- 70%7.0
- API versioning
- 100%10.0
- Usage billing and payments
- 80%8.0
- API monitoring and logging
- 70%7.0
- Faster API development.
- Tighter control over resource access with API keys and usage plans.
- Cost savings compared to server based API implementations.
While Azure API Management is also a comparable product, the teams I support are heavily invested in AWS making the use of API GW much more approachable.
- Price
- Product Features
- Product Usability
- The security provided by API Gateway is very good.
- It's very easy to implement event-based architectures.
- Very fast deployment, and you are good to go in minutes.
- The export features, such as Postman collection or the Swagger extension, are awesome.
- I think there should be another way of enabling CORS. It basically creates OPTIONS for every endpoint, which makes your API Gateway look complicated.
- The integration timeout limit is 30 seconds, which limits you into that time.
- API Gateway UI should be improved and should work correctly when more than two people are adding/editing endpoints.
- API access control
- 100%10.0
- Rate limits and usage policies
- 60%6.0
- API usage data
- 70%7.0
- API user onboarding
- 80%8.0
- API versioning
- 90%9.0
- Usage billing and payments
- 60%6.0
- API monitoring and logging
- 70%7.0
- API Gateway reduced the effort that developers and DevOps use because it provides you with a very smooth way to implement your endpoints.
- We needed to think about getting our endpoints to be resolved under 30 seconds due to the API Gateway timeout limit.
- Scalability & availability.
- Easy to deploy and customize.
- API keys and security.
- Very rich documentation and support by AWS.
- Somewhat difficult for new developers with many configuration options.
- Support only SSL secure custom domains.
- API access control
- 70%7.0
- Rate limits and usage policies
- 80%8.0
- API usage data
- 70%7.0
- API user onboarding
- 60%6.0
- API versioning
- 90%9.0
- Usage billing and payments
- 90%9.0
- API monitoring and logging
- 80%8.0
- Because deployment is easy, its reduce deployment time and support quick release.
- As cost only on what you used, easy to rapid test different services.